5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
- Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
+ Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
+ Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 2-2: Data Dictionary Concepts

File Management and the Data Dictionary


Some of the file management facility is system- or platform-specific, while application design is system-independent. From the integration of the two facilities, you can develop an APPX application without regard to the target platform, yet operate the application to take maximum advantage of the system it operates on.

The file management facility is most tightly integrated with those dictionary components that are database-dependent. The term database-dependent, or database-related, refers to what is unique to a specific database (as defined by file management).

In the APPX dictionary, permanent disk-based files are database-dependent. Each database that accesses a permanent, disk-based file actually accesses a separate copy of the file. Unstored files, temporary files, work fields, and memory files aredatabase-independent. In this case, APPX maintains a single file that is accessed by all databases.

For database-dependent files, a number of dictionary specifications provide information and defaults for, or impose restrictions on, the file creation utility in file management. These specifications include File Name, Organization, Variable Length?, Compress Records?, and Create by File Management? For disk-based temporary files (database-independent), file management refers to the dictionary specifications for file size information.

The dictionary is also integrated with file management's restructure utility. APPX uses this utility to automatically restructure files to reflect such changes as the length of a field or a change in storage type. The flag that indicates a file requires restructuring is maintained by the data dictionary when it is compiled or recompiled. Refer to the System Management Manual for a discussion of the restructure utility.

Application Design Manual                                         "Powered by Appx Software"

143

©2006 By APPX Software, Inc. All Rights Reserved